Add no-loc metadata#12833
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
There was a problem hiding this comment.
Pull request overview
Adds no-loc metadata to the PowerShell documentation hub page to prevent specific community brand names from being localized (Fixes AB#560228).
Changes:
- Add
no-loclist toreference/index.ymlmetadata.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| author: sdwheeler | ||
| ms.author: sewhee | ||
| ms.date: 03/18/2025 | ||
| no-loc: [Community, Discord, Slack, Spiceworks, "Stack Overflow" ] |
There was a problem hiding this comment.
no-loc values should match the exact text strings you want excluded from localization. On this page the card titles are "Stack Overflow", "PowerShell Slack", and "PowerShell Discord", but the list currently has StackOverflow (no space) and only Slack/Discord. Consider updating the list to the exact phrases (and removing the trailing space before ]) to ensure the metadata is effective and doesn’t unintentionally block localization of generic words like Community.
| no-loc: [Community, Discord, Slack, Spiceworks, "Stack Overflow" ] | |
| no-loc: ["Stack Overflow", "PowerShell Slack", "PowerShell Discord"] |
|
Learn Build status updates of commit 3e86aaf: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 024a931: ✅ Validation status: passed
For more details, please refer to the build report. |
PR Summary
Add no-loc metadata
PR Checklist